Motivation and Context

The following PR adds a PUT method for updating a server version (optional, not implemented by the registry but still provides the ability for other registry implementations to standardise on it)

Details:

• Path: PUT /v0.1/servers/{serverName}/versions/{version}
• Purpose: Update a specific version of an MCP server in the registry
• Authentication: Uses bearer token authentication (registry-specific)
• Request Body: Accepts a ServerDetail schema
• Response: Returns a ServerResponse on success (200)
• Error Handling: Includes proper HTTP status codes:
  • 401: Unauthorized
  • 403: Forbidden - Insufficient permissions
  • 404: Server or version not found
  • 500: Internal server error
  • 501: Not Implemented - Registry doesn't support updates

How Has This Been Tested?

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context